Displays active, inactive, or all API profiles, depending on the filter chosen when the via the "Display" button is first clicked.

Activate all API Profiles displayed in the list.

Deactivates all API Profiles displayed in the list.

If clicked, all API Types for the Custom API category will be synced.

Allows users to export API Profiles into an encrypted ".etf" file. Those exports can then be imported into other systems.

• The XML data will be encrypted during export and decrypted upon import.
• In addition, sensitive information (password and key fields) will be encrypted before storing it in the database.
• The export files will be named based on the API profile name and will utilize a custom file extension.
• Added in version 17.03.008.

Required. Enter the name of the API Profile.

Required. Defines the API Category type. Selection options are:

• Accounting API
• Custom API
• eCommerce API: EvolutionX
• Freight API
• Tax API: AvaTax, TaxJar

Defines the specific API that will be defined on this form. The options depend on the selection made in the API Type field above. Note: API Types (Providers) will define the functionality around the External System syncing and monitoring.

• Commerce Suite, QuickBooks Online
• 'User Defined' - If the Custom API option is selected in the API Category field above then users will be able to add a custom API type and caption in this field.
• EvolutionX
• EasyPost, FedEx, FedEx Legacy (version 17.00 thru 17.02), UPS, and USPS
• AvaTax, TaxJar

Fed Ex Legacy Notes:

1. FedEx Legacy - A dxpop entry is run when updating to version 17.03 that creates both a Fedex and FedEx legacy set of credentials in the dxAPIprrofiles table. If legacy credentials exist in the df_fedXXlegacy fields the system will use these as the Fedex legacy credentials. Next, the system will use the primary FedEx credential fields to create the FedEx api profile record which should exist.
2. If legacy credentials exist, the system will use them with the Ship API SOAP call. All other calls should will use the new REST APIs, and the main Fedex credentials. If these credentials are not valid the system will prompt the user '<fedex error message>. Please ensure you are using FedEx REST credentials.' This would happen if using rest credentials with dangerous goods in the ship API.
3. The FedEx Legacy credentials will be required to continue shipping Dangerous Goods. Also note however, that FedEx legacy fields need to be populated, when using FedEx as a Service Provider via Purchasing > Maintenance > Ship Via Methods, even if customers are not shipping dangerous goods

Required, except when using a type of "USPS". Displays as Authorization Code when choosing QuickBooks Online or Evolution X. This value is supplied by the vendor. This field is encrypted.

Account username. Only available when using a type of Evolution X, FedEx, UPS, and USPS.

Account password. Only available when using a type of Evolution X, FedEx, UPS, and USPS. This field is encrypted.

Option to define the company specific tax code. Only enabled when using a provider of “AvaTax”.

Defines the name/string that appears on the order lines when adding TaxJar or AvaTax taxes instead of standard taxes.

• Required if companies will use TaxJar or AvaTax.
• The value in the field defaults to “Sales Tax” but may be modified.
• This field is also used description of the tax line that will be added to sales/purchase orders when using VAT Tax functionality.

Defines the shipping account number provided by the carrier, i.e. - UPS, FedEx. Only available when using a type of FedEx, UPS, and USPS.

Only available when using a type of "FedEx".

Only one record combination of "Type" and "Facility" may be set.

When creating a new EvoX API profile this field is enabled and defaults to the production integration engine environment.

If checked, the API integration will operate in test mode. Transactions will not be processed, but users can see records/entries for orders. This field is disabled when using a Type of EasyPost.

Check to make the API Profile active.

Defaults to false, enabled only when Type = 'Follow Sales Options'. The transaction performed will be executed as tax exempt.

• This field must be checked if using the "Tax Exemption Code" field on the Order Defaults tab via Sales > Customers.

Required. Defines the name of the API Type

Read only. Will display "Custom API".

Option to select an existing Deacom External Program that will be incorporated and synced with this API Type.

Check to make the custom API Type active.

If checked, database tables associated with the API Type will be monitored when using the API.

Read only. Copy of the value in the "Name" field on the General tab.

Define the Deacom system table to be synced. Defaults to"None".

Option to define a user-defined statement that will be evaluated when filter information for the API Type.

Option to set the schedule time for this API Type.

• Only editable if the "Action" field below is checked.
• Beginning in version 17.03.006.0002, tThis field can be used even if the "System" field on the General tab is checked.
• This will enable customers to modify their own schedule times, rather than relying on Pop calls / Queries.

Defines the action / action statement that will be evaluated when filtering information for the API Type.

• Only enabled if the "Action" field below is checked.

If clicked, opens the "Sync Action" field for entry. The system will evaluate the "Sync Action" field when syncing.

If clicked, will create a new entry, based on the "Sync Filter", in the monitored, synced table.

If clicked, will update the monitored, synced table based on the "Sync Filter.

If clicked, will delete the monitored, synced table based on the "Sync Filter.

Pick list used to select the kind of AI. Options are:

• Exclude
• Remap
• Unit

Pick list used to select the part/category/sub-category classifications for the AI remappings and/or exclusions in WMS. Options are:

• All - Default. The resulting search box will be disabled.
• Category - The resulting search box will allow the user to select from Category records.
• Sub-Category - The resulting search box will allow the user to select from Sub-Category records.
• Part Number - The resulting search box will allow the user to select from all active Item Master records.

Pick list used to select the WMS form/transaction that the AI will be excluded from or remapped. Options are:

• All
• De-issue Inventory
• De-Issue Master Lot
• Final Staging Job
• Final Staging SO
• Find Inventory
• Input Production
• Issue Job
• Issue Master Lot
• Log On/Off Job
• Move Inventory
• Physical Inventory
• Pre-Stage Job
• Pre-Stage SO
• Receive IC Transfer
• Receive PO
• Reserve SO
• Ship Sales Order
• Un-reserve Inventory

Search box of all active records for Units. Only available when selecting a Type of "Unit".

• When reserving a Sales Order or Receiving a Purchase Order, if a base weight is selected with AI's for units set up on the Exclude AI form, the attached unit will be converted to the base weight unit.

Text field used to indicate the AI number that will be excluded or remapped.

Text field used to indicate the AI number that the number in the field above will be remapped to. Only available when selecting a Type of "Remap".

Pick list used to choose the desired kind of report that will generate. The only current option is "Standard".

Marks the device request as denied and populates the "Denied" date. The User will not be able to access the system.

The User who requested to be approved.

The description entered by the User requesting to be approved.

The last name of the User.

The first name of the User.

The description entered by the User requesting to be approved.

The date the request was submitted.

The date the request was marked as approved.

The date the request was marked as denied.

Marks the device request as approved and populates the "Approved" date. The record must be saved, then the User will be able to access the system.

Marks the device request as denied and populates the "Denied" date. The User will not be able to access the system.

The User who requested to be approved.

The description entered by the User requesting to be approved.

The date the request was submitted.

The date the request was marked as approved.

The date the request was marked as denied.

Displays the system-generated caption. Cannot be modified.

Indicates if a caption is user-specific or for all users.

Display only. Indicates the system default caption.

Displays the caption for the language listed. One column will be displayed for each additional Language that is added to the system.

No

No

No

No

Displays the name of the company database, up to 30 alphanumeric characters. Spaces and special characters such as ?!@#$%^&*() may not be used.

Displays the description of the database, up to 60 characters. Users will see this description in the database pick list when choosing which company to log into. The description will also appear in the form header in all system application forms.

Displays the associated database that stores the document information, up to 30 characters. Spaces and special characters such as ?!@#$%^&*() may not be used.

If checked, this database is active. Only active databases may be logged into and transacted in.

• Only one company may be set as the default.
• A default is not required.

Displays the area code or prefix for the country code.

Displays the name/description for the selected record.

Displays the appropriate mask using the number 9 and dashes. Example "999-999-9999".

If checked, the record is active. Only active records may be used in the system.

Displays the name of the Document Category.

If checked, the record is active. Only active records may be used in the system.

If checked, this Document Category will be the default when attaching documents to master records in the system.

Outbound

Inbound

Outbound

Outbound

Opens file defined in sample file box for viewing.

Imports any saved EDI Layout template.

Saves EDI layout as a template.

Name of the EDI Import, which must be unique. If a user enters a name that has already been used and clicks the "Import" button, the system will prompt the user that the name must be unique.

• Beginning in version 16.00.108, Tthe system will use the name in this field as the file name when clicking "Export" button above. If this field is blank, the system will use "EXPORT" as the file name. The following special characters would be replaced with either a + / _ character. For example, a file named " <>:"/\|?*" will have an output of "+_________.xml"
  • < (less than)
  • > (greater than)
  • : (colon)
  • " (double quote)
  • / (forward slash)
  • \ (backslash)
  • | (vertical bar or pipe)
  • ? (question mark)
  • * (asterisk)

Location of the data files to be imported on the local server.

• Files are placed here before processing. After successful processing, they are put in the Success Path location.
• Use network paths with the UNC (server) name rather than mapped drives.

Location where data files that pass the EDI parameters will be sent on the local server and removed from the Source Path folder.

• Use network paths with the UNC (server) name rather than mapped drives.

Location where data files that fail the EDI parameters will be sent.

• If, for example, the data file contains part ID’s that are not found in the Deacom system the program will send the file to the location in the Failure Path. A record for the failure will be logged in the EDI import history table.
• Note that the system will add the header and footer information to the files (successful or failed) if the file does not contain them.
• Use network paths with the UNC (server) name rather than mapped drives.

Determines if the EDI Import will be for Purchase Orders, Sales Orders, or Inventory (Adjustments).

• When processing an EDI import with a type of Inventory, all processes that occur when an inventory adjustment is made in the main application will occur. Inventory transactions occur as of the date the EDI profile is run, or with a custom date (fi_date). To accomplish this, the fi_prid (part number ID), fi_waid (facility), and fi_quant (quantity being adjusted in or out) must be populated as a result of the EDI Import. If fi_quant is negative, inventory is adjusted out, if fi_quant is positive, inventory is adjusted in. To adjust for lot controlled items, fi_lotnum (system lot number), fi_userlot (user lot number), and fi_loid (lot number ID) must be populated as well as a result of the EDI Import.

Pick list used to define the Order Type to be created by the Import. The options available depend on the Transaction Type selected above.

None

• Automatically selected and grayed out when selecting a Transaction Type of Inventory.

Purchase Order Type

• Purchase Order - Can be received as imported, no manual review required.
• Requisition - Cannot be received as imported, requires manual review and conversion to a Purchase Order.
• Purchase orders can be received automatically via EDI.

Sales Order Type

• Block Order - Cannot be shipped as imported, requires manual review. Note: Block Orders are no longer available beginning in version 17.02.006.
• Forecast - Cannot be shipped, either as imported or with manual review. Used to represent future sales demand before actual orders are received from customers.
• Inter-company Transfer
• Internet Sale - Cannot be shipped as imported, requires manual review. During import of the EDI file, an order may be saved as an internet order. At this point, the user will have to manually change the order to a Sales Order to allow the order to be shipped.
• Master Order
• Sales Order -
  • Can be shipped as imported, no manual review required or set to ship automatically. To set the automatic shipment process, the Transaction Type needs to be set to Sales Order, and the following fields, at a minimum, need to be populated as a result of the EDI Import: to_ordnum(order number), to_shipped (shipped date), fi_quant (quantity be shipped), and fi_prid (part number ID). If shipping with lot controlled items, fi_lotnum (system lot number), fi_userlot (user lot number), and fi_loid (lot number ID) must be populated as well as a result of the EDI Import.
  • Inventory already reserved to an order can be used when shipping sales orders via EDI. To accomplish this, a parsing rule for both to_ordnum and to_shipped must be created on the EDI Import routine.
  • Sales orders that have already been shipped can be invoiced via EDI. To accomplish this, a parsing rule for both to_ordnum and to_invdate must be created on the EDI Import routine.
  • Inventory can be reserved to a sales order via EDI, even if the order is not being immediately shipped. In order to reserve via EDI, the EDI Import must contain a parsing rule for to_ordnum, fi_prid, fi_quant, fi_date and at least one of [fi_attrib1, fi_attrib2, fi_attrib3 or fi_masterlot]. Note that fi_date will be used as the reserve date and fi_quant will be used as the reserve quantity, rather than a filter on which lots to reserve. Similar to fi_quant, fi_attrib1-3 and fi_masterlot. These fields indicate values that will be set after the lots are reserved, not values that will be filter on when selecting lots to reserve. All other dtfifo lots (fi_lotnum, fi_serial, fi_catchwgt, etc.) will be used as filters on which lots to select for reserving.
  • to_shipped and to_invdate rules can exist in the same EDI profile (map). If the shipment action results in a failure for any reason, the system will not attempt to invoice. (Note: The existing functionality where these actions can exist in separate profiles (maps) is still retained.)

  • NET1 payments can be applied to sales orders if the Terms specify a credit card process and the processor to be used is NET1.

Location of sample file, for reference.

Allow the user to store various notes that will remain post import/export.

Frequency to run import, if running automatically. The use of this field requires that the Deacom automation service or console is running. 

• Note: Most versions of MS Windows have automatic service restarting capabilities to ensure that if a service is stopped it can be restarted by MS Windows. If users wish to setup some type of alert service, a piece of service management software that would send out email and other alerts when a specific service is not running would need to be installed.

Address/location of FTP server. If set up, EDI import will retrieve information from Source Path on the FTP server. If a secure FTP connection is desired, set the prefix to be "FTPS://".

Port number used for clients who use the Secure File Transfer Protocol. This field will only be used for SFTP and only when it is set to a port number. (greater than 0)

Unique name of user for accessing FTP server.

Unique password of user for accessing FTP server.

If checked, indicates that system will accept invalid SSL certificates. This functionality is off by default (denying access to hosts with invalid SSL certificates).

If checked, Binary mode is used to transfer files. If unchecked, ASCII mode is used to transfer files.

Pick list used to choose the delimiter that is used between fields. Options are:

• ASCII - Used in situations where special non-printable/viewable characters will be used as field delimiters and line separators. An example would be a Field Delimiter that is a "@" and the line delimiter that is a "~" that would be inside a .txt file. When setting the ASCII values in the EDI form the user would enter the following values: Field: 064, Line: 152.
• Comma
• Other
• Pipe
• Space
• Tab

Specific field delimiter when the “Other” option is used.

Pick list used to choose the delimiter that is used between lines. Options are:

• ASCII
• New Line
• Other

Specific line delimiter when the “Other” option is used.

Memo field to define when to create a new order.

Pick list used in connection with the "New Order Condition" field. Options are:

• Order Condition Changes - A new order will be created each time the new order condition changes in the import file.
• Order Condition is True - A new order will be created each time the new order condition is true in the import file.

Memo field to define a new sales order line.

Memo field to define when to skip a line.

Memo field to define when to delete a line.

• An example of an EDI Import that uses the Delete Line Condition is available via the Configuring Inbound EDI Transactions page.

If checked, Sales/Purchase Order header information pulled via the EDI Import may be applied to multiple Sales/Purchase Orders. The process is: 

1. When the New Order condition succeeds while parsing an EDI file and the flag has been checked on the EDI setup, copy the order header information from the current order to the new order.
2. Made the current order's line count available to the new order condition expression so that it can be determined if any lines have been added to the current order or not. The field name is "linecount" and is only available to the New Order condition. An example using this feature is available on the Configuring Inbound EDI Transactions page.

Template data is used to copy and create actual EDI imports, and is not intended to be run.

Pick list used to define the Deacom field name to which data is being imported. The fields available in the list depend on the Transaction Type selected on the EDI Import form.

• EDI imports can set the Tax Region to a sales order or newly created ship-to or bill-to company. Complete information on this process is available here: Setting Tax Regions on Sales Orders and Customers. The business case for this change is situations where dropship (B2C) orders from a service like Shopify requires creating new Ship-To Customers using the "Lookup or Create" functionality.  Due to this, the Ship-To doesn't exist and therefore unable to pull in the Tax Region from the Ship-To.
• Users can set GL Overrides, during EDI Imports, on newly created Bill-Tos and Ship-Tos by adding all GL Override fields (all fields in the dmover table) to the dropdown in this field. These fields are only available when the "Transaction Type" field on the EDI Import form is set to "Sales Order" and only when using the Lookup or Create option on Bill-To/Ship-To records.
• Bill-To and Ship-To User Defined Fields (beginning in version 17.02.106) are available for selection in this field.

Memo field to define when to import into the selected field.

Pick list used to select the method to define data. Options are:

• Lookup - Look up data in Deacom Lookup Table, using Lookup Expression.
• Lookup or Create - Only available when selecting the Sales Order Bill-to Company" (to_biid) or "Sales Order Ship-to Company" (to_shid) in the "Field" field on the Edit Parsing Rule form.
• Expression - Use parsing expression to define field data.

Notes:

1. The Parsing Rule form was enhanced so that when creating a new Ship To Company using the "Lookup or Create" type, and a Bill-To Company is being created as well during the EDI Import, and a Ship-To Company is not specified in the "Create Same As" field, the system will use the values from the new Bill-To Company to set the defaults on the newly created Ship-To Company. See the list below regarding parsing rule exceptions when creating Ship-To Companies via "Lookup or Create" in version 16.06.046 and above.
   1. If the import profile has a specific parsing rule for any dmship fields, the system will use those instead of copying from the Bill-To Company.
   2. If a parsing rule exists to override a value on a Bill-To, that overridden value will not propagate to the newly-created Ship-To or to the Order.  Similarly, if a parsing rule overrides a value on a Ship-To, that overridden value will not propagate to the Order.  For example, if the intent is to override a value on the Bill-To and have it flow to the Ship-To and Order, a parsing rule must exist for each override (one for the Bill-To, one for the Ship-To, and one for the Order).
2. Version 16.06.078 further enhanced the Parsing Rule form so that Wwhen using the "Create Same-As" button to create a Bill-To or Ship-To via EDI Import the system will prevent the following fields from being imported: Name, Contact, Phone, Ext, DBA, Streets, City, State, Zip, Country, County, Fax, Email, Dear, Salutation, Notes. The code was also changed to add an empty string to the specified fields above so that they are not imported unless explicitly done so by using a parsing rule. This was done to ensure that a Bill-To or Ship-To that is created via EDI Import will NEVER have its address or contact fields populated from the "source" Bill-To or Ship-To.
3. Bill-To and Ship-To User Defined Fields are available to EDI Imports when Lookup or Create.

Pick list used to select the Deacom table to look up data in, when using a "Type" of "Lookup".

Expression to define the table lookup. The expression will usually contain the name of the Deacom field stored in the table indicated in the "Lookup Table" field above. 

• Note: This field uses TSQL code and not the traditional SQL code documented in the "Functions & Operators" library.

Used in connection with the importing or creation of bill-to and ship-to customers through EDI. This field will only be available when selecting "Lookup Or Create" in the type field above. When this field is enabled, users may select a bill-to or ship-to customer (depending on which one was chosen in the field "Field" at the top of the form) that represents the record that will be copied and used to create the new customer record if the lookup fails. Additional information is available in the "Import & Creation Of Customers" section further down on this page.

Allows you to add a new Form layout to your list of user-defined forms. When clicked, a search box opens to allow you to select the base form layout to use.

Allows you to modify the selected form layout by opening the Form Layout Editor.

Allows you to choose Active, All, or Inactive form layouts to show in the grid.

Allows you to Modify this form layout (MainMain).

When viewing your inactive forms, this will bulk activate the inactive forms visible in this list.

When viewing active forms, this will bulk deactivate the forms visible in the list.

Note: Occasionally a form layout can become corrupted and the only way to inactivate it is to filter the Form Layout grid down to just that form layout and click Deactivate All.

Allows you to import a Deacom .uform file for this layout from other Deacom systems.

Ability to export a Form Layout to a .uform file.

Depending on which Object selected in the tree allows you to add elements to the object. This is hierarchical and dependent on the object chosen.

Allows you to modify the element selected in the tree or in the WYSIWYG editor on the left.

Allows you to delete the selected element. Using this button is the only way to delete an element from your form.

Allows you to save the form layout design you created.

Notes:

1. Once a form layout has been modified the layout becomes unique to your instance of Deacom. Upgrades will not alter the elements or layout of this form, and new functionality will not be added to this form. If you want to add functionality to your user form layouts, you will need to use the Add New button and build the functionality into the form layout.
2. Whenever a user saves modifications to a form layout, the system will automatically log these changes in the Modification report via System > User Modifications. (beginning in version 17.04.009)

All users, User Group, or Specific User. This option defines what users this form layout will apply to.

Contextual search field. Only enabled for Layout For types of “User Group” and “Specific User”.

Allows you to choose what this form layout is for. All, Desktop, or Mobile. Defaults to All.

A short description of the purpose of the layout. For instance, “Customer Service – Fast Order Entry”.

Note: You should always update your Description each time you alter the form layout. We recommend adding the date modified to your description text.

The form itself is the container for all other objects on the form.

Sections contain other objects and can either be two columns wide or one column wide.

Section Frames contain Sections, every Section in a Frame becomes a Tab.

ToolBars contain buttons and are always either at the top of a form or the top of a grid.

Buttons on the toolbar, such as the "Add" button.

Vertical line separators that allow for separation between groups of buttons.

Boolean state boxes that are either checked or unchecked, such as "Active". There is also an option for Custom Criteria, which can search for User Defined Fields.

A control that allows for selecting a color, such as the Work Flow Color.

Also referred to as a "Dropdown" or a "Picklist", allows for selection from a pre-defined group of options. There is also an option for Custom Criteria, which can search for User Defined Fields.

Allows for the selection of a date. There is also an option for Custom Criteria, which can search for User Defined Fields.

Allows for the selection of a file, such as in View Docs.

Allows for the selection of font, such as the Grid Font in System Options.

Displays data in a row / column format.

Allows for the entry of data that is multi-line and free-form.

Allows for the entry of data that is multi-line and free-form, except without drilling down (such as the send email form).

Allows for the recording of a signature, such as in the Point of Sale application.

Allows for lookups of records for assignment purposes, prevalent on editing forms and pre-filters. There is also an option for Custom Criteria, which can search for User Defined Fields.

Allows for single line of text entry.

A variant of the TextBox that allows for quick phone calls in the mobile application.

A variant of the TextBox that allows for launching of a URL on click.

Allows for the recording of time to accompany a date.

Displays the name of the Object selected from the drop down list. Options are:

• Section
• TileSection (beginning in version 17.04.005) - Added to support TileBoxes fields. TileSections are different from regular Sections in that the fields will fill the entire width of each column. TileBoxes is designed with built-in padding so there will be gaps between them even though they are lined up edge-to-edge.

Controls what happens for this element when the "Save" button is executed/clicked. Options are:

• Follow System Option (default) - the Save button will work according to the selection made in the "Save Button" field on the Company tab via System > Options.
• Save - the information in the field/form will be saved to the database.
• Save And Close - Information entered on the form is saved and form will be closed. Note that all securities related to the fields/form are validated. If a security or prompt prevents the save, the form will not be closed.

Controls how number values will be displayed and is used for formatting purposes only. (i.e. 999-999-9999 for phone number.) Use "9" for digit placeholders.

• Other characters print as written. (i.e. Comma, Decimal, and Percentage sign and these signs , . % may be used in the mask)

Determines if the user would like prompts if the input in this field matches other records in the database. The options function as follow:

• No - Default state, does not check the data in this field against other records or prompt.
• Prompt - Alerts the user that the input matches another record, but the form can still be saved.
• Yes - Alerts the user that the input matches another record and does not allow the form to be saved until changed to something unique.

If checked, the systemwill support both folder selection and multi-file selection in fields with a Type of "FilePicker"

• The appropriate field in the system will then display two icons: a file icon and a folder icon:
  • File icon - displays a standard Windows type form, except that now, users can select multiple files by using the standard Windows functions of Crtil and mouse or Shift and mouse. Note: if the "Enable Folder Picker" box is not checked, users will still see the File icon but will NOT be able to select multiple files.
  • Folder icon - display a standard type Windows type form allowing users to select a specific folder.
    • The folder option is useful for the Deacom AI AP Invoicing feature l be allowing folder selection for submission of invoices.
    • When using this option, the form will display an "Upload" button which is how users will confirm the folder selection. When this button is clicked users may see a Chrome pop up asking for confirmation of the upload.
• This field was added in version 17.03.009.0000

If checked, the selected element will have automatically encrypted contents, when entered, rather than relying on doing it manually. These fields will show as ****** in forms and tooltips.

• Added in version 17.03.004.

This applies to scripting only. Users are strongly encouraged to use the scripting method Event.Invoke() instead of this property.

If checked, other changes in the system that effect this element will cause changes to this element. If unchecked, this element will remain the same regardless of other changes in the environment.

Allows you to add a new event to this element property. Available events depend on the property selected in the Edit Element. 

Allows you to modify the selected Event grid entry. This along with double-clicking the entry in the grid is how you will edit the script you created.

#Engine=Scripting

function lfUrl()

{

var loPayload = {

"Filename": "https://canto-wp-media.s3.amazonaws.com/app/uploads/2019/08/19194138/image-url-3.jpg", "Content": ""

};

return Convert.ToJSON(loPayload);

}

lfUrl();

No

leave blank

checked

unchecked

unchecked

If clicked, opens the Edit Grid Layout form to create a new user version of the selected grid.

• This button is used when creating a user version of a grid to add, remove, or modify fields.

If clicked, opens the Edit Grid Layout form to modify the selected user grid. System grids may not be modified.

If clicked, deletes the selected user grid.

If clicked, opens the Edit Grid Layout form to create a new user version of the selected grid.

• This button is used when creating a new user report by copying the grid from the system version or another user version of the report.

Displays the name of the grid.

Displays the title with which the grid/form loads, which may be modified when adding or modifying user versions of system grids.

Displays the User or User Group for which the grid was configured, or displays as "System" if it is a system grid.

If clicked, opens the Edit Grid Column form to add a new field to the grid.

If clicked, opens the Edit Grid Column form to modify the selected field.

If clicked, deletes the selected field from the grid.

If clicked, allows the user to sort the order in which the fields listed will appear.

Displays the name of the grid.

Displays the name of the grid as referred to in the code.

Displays the title with which the grid/form loads.

Pick list used to determine if this grid will be used for all users, a specific User, or a specific User Group. Note that an All Users version of a system Grid Layout must exist before creating a Grid Layout for specific Users or User Groups.

• Security settings will determine which options are selectable for each user.

Search field used to select a specific User or User Group to assign this grid.

• Displays as "User" or "User Group" when "Grid For" is set to "Specific User" or "User Group", respectively.
• Only available when "Grid For" is set to "Specific User" or "User Group".

Searchbox that allows a user to apply a previously made active filter into the selected grid, implementing fields such as Logic, Operator, Value, and Type.

Advanced Filters can not be applied to BI Pages or Favorites.

• To delete an Advanced Filter, navigate to the Filter/Sort button on the toolbar of the selected grid, highlight it, and hit Remove.

Pick list used to dictate how the user grid will refresh. Options are:

• No - Do not refresh.
• System - Follow the settings for the system grid.
• Yes - Automatically refresh.

Pick list used to dictate how the user grid will refresh when its' parent form is refreshed or modified. Options are:

• No - Do not refresh.
• System - Follow the settings for the system grid.
• Yes - Automatically refresh.

Pick list used to indicate the application where the grid will be applied. Options are:

• Mobile
• Desktop (main application)
• All (both Mobile and Desktop)

Notes: 1. Users can create separate grids, one for Mobile and one for Desktop from the same system grid. 2. If changing this setting to All and grids exist for either Mobile or Desktop, the system will delete those grids.

Defines the number of columns, beginning on the left, that will be pinned or frozen on the grid. Example: If your report has 30 columns, entering a value of 2 will result in the two leftmost columns being frozen as the user scrolls from left to right.

• The system will display a vertical line to indicate which columns are pinned.
• Users may drag the vertical line to the right or left to change the number of pinned columns. Note that this change only effects the current session. Once the user exits the grid, the system will revert back to the value entered in this field.
• Double clicking the "Resize Columns to Fit" button, located at the top left of the grid, causes the grid to revert back to the value in this field.
• The number of pinned columns does not impact the printing of the report or the export to Excel feature.

If checked, indicates that the mobile specific grid for this system grid will be made available to mobile application. The mobile specific grid is a simplified version of the default system grid containing the core information for the report.

If checked, the system will automatically refresh the contents of the grid.

If checked, the system will automatically refresh the contents of the grid once its' parent form is refreshed or modified.

Enter the name of the Export Format.

Select "Print Out" or "Text."

Select an available report.

• This field is enabled and required when selecting "Print Out" Type.

• This field is enabled and required when selecting "Text" Type.
• All fields available to the grid layout should be available to the Text field and it should be treated like the Message field on triggers where fields within carets <<>> should be evaluated as variables and returned. There should be one line per record on the grid exported into a .txt file when exported.

Displays the name of the field.

Memo field used to store an expression.

Search field used to select the Caption for the Field selected.

Displays how wide the column will appear on the grid.

Option to enter pre-defined FoxPro format options such as left, center, or right justify.

• Rarely used; generally left blank.

Controls how number values will be displayed and is used for formatting purposes only. (i.e. 999-999-9999 for phone number.)

• Use "9" for digit placeholders.
• Other characters print as written. (i.e. Comma, Decimal, and Percentage sign and these signs , . % may be used in the mask)

Pick list used to determine if the Title should appear in Bold, Italic, or Standard font.

If checked, the first double-click on a column header sorts in descending order.

If checked, indicates column will be summed and results will be displayed underneath the toolbar on the report the next time it is displayed.

• Only numeric fields can be summed.

If checked, indicates this field will be displayed in the print preview.

• Applicable for user-defined columns that have this flag set to true.

If checked, requires field to be entered in the following time format: MM:HH PM/AM.

Defines the name of the language.

Defines the culture used with the specified language. The culture selected will enable the system to use the date/time/number formatting generally defined for that culture when printing a sales report or part form. When printing, the date/time/number formatting will follow that of the Culture set for the Language on the Bill-To or Ship-To, depending on which is assigned to the Language field for the report/part form.

• The list of Cultures is provided by an API call.

Defines the length of the field labels for this language.

Defines the length of the actual fields when using this language.

If checked, this record is active. Only active records may be used in the system.

Memo field that stores the system version of the Prompt.

Indicates the name of the Register.

Indicates the Facility in which this Register is used.

Pick list used to select the EMV processor created via Accounting > Maintenance > Credit Card Processors.

• Added in version 17.02.016.

Defines the Terminal ID used for the EMV register/device.

• Added in version 17.02.016.

Pick list used to select the Printer to which this Register should print documents, including those installed via Deacom Local and Deacom Cloud Local.

If checked, this record is active. Only active records may be used in the system.

If clicked, opens the Form Layout for the current grid.

Displays the name of the field that prompts the selected searchbox. Use the drop down arrow to see the list of available fields.

Memo field used to store the user-configured name of the searchbox.

Indicates the type of data displayed in the field, either Character, Date, or Numeric.

Indicates the width of the column in the form.

Option to enter pre-defined FoxPro format options such as left, center, or right justify. Rarely used; generally left blank. This field can be used create a variety of formats for output generated from Field controls by creating a format string expression. See the Basic Objects and User Interface help page for additional information.

Displays the mask used to input the character, date, or number for the field.

Option to select if the selected field will be a primary or secondary field when using the Deacom Mobile application. Primary fields will be displayed in a larger font and generally on top of secondary fields.

Text box used to enter the user security question

Allows the user to copy another Trigger to use as a base to create a new Trigger.

Displays lists of fields and variables that can be used in the Trigger.

Defines the name of the Trigger, which must be unique.

Pick list used to define when the Trigger will fire. Options are:

• Both - trigger fires when record is updated or inserted.
• Insert - trigger fires when a record is inserted in a table.
• Update - triggers fires when a record is updated in a table.

Pick list used to indicate the Deacom table that will be used as the source of the Trigger.

Pick list used to select the result of the Trigger firing. Options are:

• EDI - Creates an EDI file.
• HTTP POST - If selected, Triggers will post to a URL.
• HTML Email - Sends an email in HTML format.
• Plain Text Email - Sends an email in plain text format.

Information or text that will populate the subject line of the email.

• This field is disabled when selecting a "Output" of "HTTP POST."
• The system will use the information or text in this field to name any files sent via the "Attachments" tab.

Address for email or folder for EDI file or, when the "Output" field is set to "HTTP POST," the URL where the trigger will post.

• Multiple email addresses may be used, separated by semicolons.
• Only one file path is allowed, and may contain a string of text and field names indicating what the file should be named when it is saved to the folder.
• When using the "Attachments" tab on this form, this field defines the email or folder address for the attached files.
• OAuth2 support is available for Trigger Emails. If this field is set to OAuth2 and sending an email using trigger credentials, the system will use OAuth2 to send the trigger email.

Address for an email to be sent a carbon copy, which will be present on the recipient's header. Only available when Output is set to "HTML Email" or "Plain Text Email".

Address for an email to be sent a blind carbon copy, which will not be present on the recipient's header. Only available when Output is set to "HTML Email" or "Plain Text Email".

Defines the conditions that must be met to fire the Trigger.

• Only fields in the trigger table are available to the Conditions.
• Users can use <<>> expressions to add table fields to the message, subject, and destination fields.
• The "Show Fields" button can be used to determine what fields and variables can be used and any SQL Server functions can be used within the brackets.
• This field uses T-SQL code and not the traditional Deacom syntax as documented in the "Functions & Operators" library.
• The expression in the Conditions field must evaluate to a logical TRUE or FALSE, and should be written as if it were to be used in a T-SQL conditional statement, such as CASE WHEN [Conditions Expression] THEN [trigger should fire] ELSE [trigger won't fire] END

Message body for email or contents of EDI file.

• Utilizes FoxPro functions.
• The lc_username variable may be used in this field to specify the name of the user that made changes to the specified Table or Condition.
• When selecting a "Table" of "Sales Order Header" and a "Trigger Event" of "Update", the LOTINFO and MASTERLOTINFO tags can be used in Triggers.
• The BYTESTOSTRING() function can be used in this field to parse the dxedihistory.eh_msg field from bytes into a larger string.
• Additional information is available via Deacom Basics > Functions and Operators Library.
• If the "Output" field is set to "HTTP POST," the Message field will be a JSON string that the user generates. Upon processing the trigger, the fully parsed and executed message field will be converted from JSON to a dictionary and the results of that dictionary will be sent as HTTP POST keys to the URL. If the post is successful (HTTP 200) the text response from the server will be inserted in the trigger history as part of the success entry.

Used to enable a delayed action in a Trigger. In other words, it is used to hold the expression to calculate the date and time when a Trigger should fire.

• Example: DATE() + 2, with the Trigger to set to fire for the update/insert of SO headers.
• Behind the scenes, the system contains a table, dttrigdel, with the fields listed below.
  • td_tgid = Trigger ID
  • tg_id = ID
  • td_recid = Trigger Record Table
  • td_table = Trigger record table
  • td_delivery = Date/time of scheduled fire
• The system will check to see if the Trigger has valid delivery expression.
  • If valid, the system adds a record to the dttrigdel table and adds history telling the user the Trigger has been scheduled for the date/time specified.
  • If not valid, the system will add history to the History / Performance report or the View EDI Import History report with a message stating invalid delivery expression.
• If the delivery date is in the past, fire trigger as normal. A timer has been added to the automation service to fire when restarted and every 30 minutes. Timer will check all Triggers to be delivered and compare them to the current date/time. If the date/time is greater than the delivery date/time, fire the trigger.

Designed to handle situations where reminders to a Vendor need to be sent at various times and on various dates.

• Can be used in connection with the "Delivery Expression" field, which can be set to fire to determine when a Trigger should fire if it is supposed to be delayed. In this case, this field should fire at the actual time that a Trigger is going to be delivered (i.e. the deferred date; For example, 14 days before the "Due To Dock" date (tp_duedock)). This is different than the "Condition" field because "Condition" is a SQL condition for whether the Trigger should even fire at that level and occurs at the time the actual SQL function occurs.
• This field has all of the same fields available to it as the other fields on the Trigger form.
• Systematically, the logic of this field is as follows:
  • If the type evaluated is not boolean, fail the Trigger for invalid expression.
  • If expression evaluates to false, note that the Trigger was not executed in trigger history. Otherwise, execute the Trigger.
• This field uses the traditional Deacom syntax as documented in the "Functions & Operators" library and not T-SQL code. The expression in the Delivery Conditions field must evaluate to a logical TRUE or FALSE, and should be written as if it were to be used in a Deacom conditional statement, such as IIF([Delivery Conditions Expression], [delayed trigger should execute and not write to trigger history], [delayed trigger won't execute, but writes a note to trigger history])

Memo field used to define a custom query that allows greater functionality.

• Can reference fields just like the "Subject", "Destination", and "Message" fields and any Deacom database fields may be used.
• Including a field in Custom Query makes that field available to the trigger.
• Only single lines can be used from the query results and must be selected using the SELECT TOP 1 function to accurately utilize the fields returned.
• Once the Custom Query is set, the Edit Trigger Message can use fields on the query to return results from the top line of the Custom Query results.
• This field uses SQL code.

User can add various notes to the Trigger such as identifying the author or for code explanations.

Only available when selecting an "Output" of "EDI." Defines the address/location of FTP server.

Port number used for clients who use the Secure File Transfer Protocol. This field will only be used for SFTP and only when it is set to a port number. (greater than 0)

• Only available when selecting an "Output" of "EDI."

Only available when selecting an "Output" of "EDI." Defines the unique name of the user for accessing the FTP server.

Only available when selecting an "Output" of "EDI." Defines the unique password of the user for accessing the FTP server.

Pick list that allows users to enable a file encoding type of UTF-8 or Windows Code Page 1252.

• Only available when the "Output" field is set to "EDI".
• File encoding of Window Code Page 1252 is particularly useful when dealing with extended characters.

If checked, the Trigger is active and will fire according to the conditions set.

If checked, this record is used as a template to create other Triggers via the "Copy Trigger" button.

• Triggers flagged as "Template" do not fire.

If checked, the system creates a new line in the message for every new line item on a Sales Order.

Only available when selecting an "Output" of "EDI." If checked, indicates that system will accept invalid SSL certificates.

• This functionality is off by default (denying access to hosts with invalid SSL certificates).

Search box used to select the Grid Layout that will be attached to the trigger email or placed in the location specified in the "Destination" field on the General tab of this form. The list contains all active Grid Layouts in the system.

• Disabled when the "Output" field on the General tab is set to "HTTP POST."
• The "Output" field must be set to "EDI" in order for the Grid Layout to be placed in the Destination location.

Search box that displays active Report Layouts based on the entry made in the "Table" field on the General tab. For example, if the Job Header (dtjob) table is selected, only Report Layouts with a type of "Job" will be visible in the list.

• Only enabled when the Grid Layout field above is not empty.
• The "Output" field must be set to "EDI" in order for the Grid Layout to be placed in the Destination location.

Opens the Edit User Access form, which is used to set security permissions for the forms, fields, and buttons throughout the system.

• Individual Users inherit the permissions of the User Group to which they are assigned, with permissions set on the individual User level overriding those set on the User Group level.

Opens the Edit Doc Access form, which is used to set permissions for Document Categories in the system.

Opens the Edit Group Grid Access form, which is used to set permissions for Grid Layouts/reports in the system.

• Setting the security on this form also sets the same security for the User Group in System > Maintenance > Grid Layout Security.
• The title of the Grid Layout, which represents the name that appears to the user in the system, can be added to the Edit Group Grid Access form by adding the c2_caption field to the Edit Group Grid Access Grid Layout.

Allows the user to assign Published Data elements, such as Graphs to the selected User Group.

Allows the user to copy Favorites from a User and assign them to this group.

Defines the name of the User Group, such as Accounting, Production, Quality Control, etc.

Pick list used for WMS only to determine if all, Maintenance only, or Production only Jobs will be auto filled when selecting Jobs using the WMS > Issue Job transaction.

Option to set the Issue Type (via the "Type" field) for this User Group level when issuing and staging inventory in the main and WMS application.

• Options are Default, Job, and Staging-Job.
• Added to remove the need for users to select the issue type on scanners. A typical example would be users in a warehouse group typically staging inventory while production workers would typically issue directly to jobs.
• The hierarchy to set the issue type field in the WMS Issue Job transaction is:
  • The "Issue Type" field on the User Group
  • Then the "Issue Type" field on Job Categories
  • The "Issue Type" field in Production > Options.
• If "Default" is selected in this field on the User Group form, the system will fall back to the previous hierarchy of Job Category, then Production > Options to set the issue type field.
• Added in version 17.04.006.

If checked, this record is active. Only active records may be used in the system.

Displays the name of the User being modified.

Limits the user to create and view records with the Facility specified.

• When a user that has a Facility restriction is creating a BOM, they may leave the "Facility" field blank or select the Facility to which they are restricted. This option was added to support companies that do not use Facility-specific BOMs but still wish to utilize Facility restrictions elsewhere in the system.
• Revision Facility Security is also available and is used to control which User Groups have access to view or edit Facility-specific BOM revisions.
• This restriction also applies when using the "Availability"and "Locations" button on the Item Inquiry form and when using the "Availability" button on the Edit Sales Order Line form.

Limits the user to create and view records with Facilities in the Facility Group specified.

• This restriction also applies when using the "Availability" buttons on the Edit Sales Order Line and Item Inquiry forms.

Limits the user to only view and create transactions tied to the Sales Rep specified.

• If a user has a sales rep restriction, that restriction will be used to filter sales order work flows so that only orders with a sales rep assignment that matches the user restriction will be displayed. If the user has no sales rep restrictions, the user will be able to view all sales order work flows.

Limits the user to only view and create transactions tied to Sales Reps in the Sales Group specified.

Limits the user to only view and create transactions tied to the Territory specified.

Limits the user to only view and create transactions tied to the Territory in the Territory Group specified.

Limits the user to only view and create orders tied to the Broker specified.

• Sales Order and Customer search boxes filter records to the restricted Broker when a user is Broker restricted.

Limits the user to only view records and transactions tied to the Formulator specified.

Limits the user to only view records and transactions for the Item Planner specified.

• This restriction also applies when issuing materials to Master Lots, both in the main and WMS applications.

Limits the user to only view transactions tied to the Labor Group specified.

Limits the user to only view and create records (via CRM, Ticket Reporting, etc.) for the Contact specified.

• This restriction also applies to notes from users with the same Contact or notes from users without a Contact restriction.

Limits the user to only view and create records and orders for the Bill-to Company specified.

• In addition, users will only be able to view or modify the selected company via Sales > Customers.
• Separate security exists to control Customer modify access.

Limits the user to only view and create records and orders for the Ship-to Company specified.

• In addition, users will only be able to view or modify the selected company via Sales > Customers.
• Separate security exists to control Customer modify access.

Limits the user to only view and create records and orders for the Vendor specified.

• In addition, users will only be able to view or modify the selected Vendor via Purchasing > Vendors.
• Separate security exists to control Vendor modify access.

Limits the user to only issue, pick, and ship (without assigning Lots) from within the Zone specified.

• This essentially breaks down to inventory that is in Locations that are in the user's Zone.

Pick list used to determine if the user is allowed to access legacy only, web only, or both versions of Deacom.

If checked, the user may only view reports for Sales Orders they entered themselves.

• Example: A user with a Facility restriction and this flag checked will only be allowed to view orders they entered in this Facility.

If checked, the user may only view reports for Purchase Orders they entered themselves.

If checked, and the user has a Facility or Facility Group restriction, all part number search boxes in the system will only display parts with an active item facility (dmprod3) record matching their Facility or Facility Group restriction can be seen.

Displays a list of companies a user may login to Deacom for.

Opens the Edit User Access form, which is used to set security permissions for the forms, fields, and buttons throughout the system.

• Individual Users inherit the permissions of the User Group to which they are assigned, with permissions set on the individual User level overriding those set on the User Group level.

Opens the Edit Doc Access form, which is used to set individual user access to Document Categories.

• Access to Document Categories can also be set at the User Group level via Document Category Security.

Opens the Edit Grid Access form, which is used to set permissions for Grid Layouts/reports in the system. The form displays a list of all Grid Layouts together with columns indicating the user's User Group access and the individual user's access to the respective Grid Layouts.

• Users inherit the permissions of the User Group to which they are assigned. User-level access control can be used in situations where the specific user needs access to additional Grid Layouts besides those available for the User Group, or in situations where the specific user will be denied access to a few specific Grid Layouts that are permitted at the User Group level.
• The title of the Grid Layout, which represents the name that appears to the user in the system, can be added to the Edit Grid Access form by adding the c2_caption field to the Edit Grid Access Grid Layout.

Opens the Edit User Restrictions form, which is used to limit Users' access to records and functions within Deacom.

Opens a mover form listing all BI and Graphs configured as Published Data that allows the user to assign reports to the selected User.

• Records moved to the Destination section will appear in the BI section of the main application.

Allows the user to copy the Favorites, which appear in the left-hand navigation pane of the main application, configured for a different User.

Defines the user's first name.

Defines the user's last name.

Defines the username that will be used to log in to the system, e.g. "asmith".

• Deacom will not ask for credentials to be entered, and will launch automatically, if the Deacom Login Name matches the Windows user name. Note: this only works for Classic and not the .Net version
• Deacom always uses the login name even with LDAP. If using a LDAP login name, the user must enter it in the Deacom login name (us_login)
• In version 17.02.007 this field was expanded to 60 characters.

Defines the user's network username. Used in connection with the "LDAP Domain" field in System > Options . Authentication tab to allow users to login into Deacom applications (WMS, Cash Register etc.) using their Deacom username and password.

• If the LDAP Domain is set up in System > Options > Authentication tab and the user has an LDAP user in their user record, Deacom authenticates using the Deacom username (us_login) with the user’s LDAP password. The LDAP User is only present to connect the Deacom record to the LDAP record, NOT to authenticate with that LDAP username.
• If the user wants to use their LDAP user name in Deacom, they currently have to make sure that us_login = us_ldapuser.
• This field is unavailable if the "Access Deacom Restart" field is checked.

Defines the user's password.

• A best practice when setting up a new user is to enter a temporary password and check the "User Must Change Password At Next Login" flag.

Confirms the password.

Defines the user's pin code used to login to the POS application.

Search field used to assign the User to a User Group.

Search field used to assign the User a Language, if different than the default.

Dropdown menu where users can have the system scale the size of fonts in the Deacom application based on the current monitors screen:

• Width
• Height
• Maximum

The default setting is "Width" in which case the system scales the fonts size based on the users screen width resolution setting. The option to change the scaling is helpful when users need to better adjust the screen in order to improve font size/rendering for Deacom top menu options and pre-filters more clearly, including monitors with 4x3 aspect ration. Example - If your current browser dimension/screen resolution is 1920 x 1280, and this field is set to "Height", the application will use this (1280, or 12.8) in order to perform the scaling calculations. If you choose to set this field to "Maximum", the system will perform both height and width calculations using the highest values returned.

Defines the email address for the user.

Defines the username for the selected user.

Defines the encrypted password for the user.

• This field is not required (as of version 17.01.041) when using OAuth2 authentication.

Option to specify an email signature on outgoing emails.

Links the User profile to the user's Outlook Contacts.

• Example input: C:\Users\<<user>>\AppData\Local\Microsoft\Outlook\<<emailaddress>>.ost

Links the User profile to the user's Outlook Calendar.

• Example input: C:\Users\<<user>>\AppData\Local\Microsoft\Outlook\<<emailaddress>>.ost

Pick list used to specify the default printer for this user when logged into the WMS application. The "None" option may be used to allow users to move to different locations in a warehouse or plant and select different printers on the scanner without being restricted to the printer set on their user record in the system.

Defines the keycode on the scanner that will be used to initiate voice input/recognition for this specific user. Options are: Custom Keycode, KEYCODE_BUTTON_L1, KEYCODE_BUTTON_L2, KEYCODE_BUTTON_R1, KEYCODE_BUTTON_R2, KEYCODE_PROG_YELLOW, and None.

• When selecting the "Customer Keycode" option, use the WMS Record Key field below to define the keycode.
• This same field exists in Inventory Options. The WMS application will evaluate the user setting first, then the settings in Inventory Options if the user setting is blank to determine the default value on the scanner. Note that if the setting for this field on the scanner is changed, it will save back to this field on the User record.
• Supports the use of voice commands for menu navigation and button selection on scanners.

Defines the user defined keycode to initiate voice input/recognition on the scanner.

• Only available when selecting the "Custom Keycode" option in the WMS Record Button field above.
• This same field exists in Inventory Options. The WMS application will evaluate the user setting first, then the settings in Inventory Options if the user setting is blank to determine the default value on the scanner. Note that if the setting for this field on the scanner is changed, it will save back to this field on the User record.
• Supports the use of voice commands for menu navigation and button selection on scanners.

Option to set an on screen recording button in the WMS application. Options are Hide, None, and Show.

• The recording button initially displays in the top right corner but may be moved.
• Supports the ability to select buttons and navigate on the scanner when speaking a menu name or number.
• This same field exists in Inventory Options. The WMS application will evaluate the user setting first, then the settings in Inventory Options if the user setting is blank to determine the default value on the scanner. Note that if the setting for this field on the scanner is changed, it will save back to this field on the User record.
• Supports the use of voice commands for menu navigation, button selection, and button commands on scanners.
  • Voice input is available for the following button commands in Android WMS: 'Undo', 'Save', 'Exit', 'Continue', 'Next', 'Previous', 'Ok', 'Yes', 'No', 'Refresh', 'Print', 'Lines', 'Stage', 'Apply', 'Lots', 'Find', 'Details', 'Issue', 'All, 'Finish', 'Reserve', 'View', 'Quarantine', 'End Job', 'Back'

Displays the date the last time the user changed their password.

Defines the number of minutes the user can be inactive on a form in the system, including the WMS system, before they are logged out and forced to log back in.

• When a user is timed out, they will receive a prompt indicating this and will be taken back to the login form.

Displays the date of the user's last successful login attempt.

If checked, this record is active. Only active records may be used in the system.

If checked, the user may access the main Deacom application.

If checked, the user may access the Warehouse Management System (WMS).

If checked, the user may access the Tracker, used to enter support tickets and monitor issues.

If checked, the user must change their password the next time they login to Deacom.

If checked, indicates the user is currently inactive.

• The system has a hardcoded number of 5 attempts allowed before this flag is set on the user record.

If checked, emails between this user and Contact People with the "Monitor Email" set to an option other than "None" will be tracked and stored as Contact Notes on the Contact record.

• Users with this functionality should archive old e-mails to lessen the load on the server.
• If this field is checked, values must be entered in the "Email User" and "Email Password" fields via the "Email Settings" option available when clicking the 'Person' icon on the main menu.

If checked, the User will only be permitted to access one Deacom application (Cash Register, WMS, Mobile, DSD, Tracker, AutoFinisher, and Main App) at a time.

• If a user attempts to log in to an app while they are already logged into a different platform, they will be prompted with "You are already logged into <<Application Name>> and are only allowed to be logged into one application at a time. Do you want to continue with this login and terminate the other session?"

If checked, and a new printer is selected via File > Settings, the system saves the user's printer selection in a cookie and reloads it on their next login as long as they are using the same browser.

• Useful so that users will not have to continually reset their printer assignments each time they log in/out of Deacom.
• Specifically, when a user logs in, the system will first wait for Deacom Local and Deacom Cloud Local printers to sync. After they sync, the system checks the cookie to see if it is filled in and matches a printer currently in the printer list. If so, the system changes the selected printer for the session. If no match is found, the system will stick with the default printer.

If checked, the user will require device approval authentication prior to logging into Deacom.

• The default for this field is provided by the "Device Approval Required" field on the Authentication tab in System > Options.

If checked, the user will require email authentication prior to logging into Deacom.

• The default for this field is provided by the "Email Authentication" field on the Authentication tab in System > Options.

If checked, the user will require security question authentication prior to logging into Deacom.

• The default for this field is provided by the "Security Question Authentication" field on the Authentication tab in System > Options.

If checked, when Deacom Local is running (Windows only) emails are opened using the Outlook desktop application rather than within Deacom.

• If Deacom Local is not running, the email will open within Deacom, regardless of whether this flag is checked.

If checked, the system will use the LDAP Password on this form when emailing from Deacom.

Indicates the general selection of users that the WMS form will be used for. Options include All Users, Specific User, and User Group.

Select the specific user or user group to which the user version of the WMS form layout will be assigned, as effected by the Form For field above. Differences are as follows:

• Selecting "All Users" in the Form For field will grey this field out as it is not required.
• Selecting "Specific User" in the Form For field will make this field become a search box for valid system users.
• Selecting "User Group" in the Form For field will make this field become a search box for valid system user groups.

Search box to select a valid Barcode Format. 

Indicates the WMS form that is being displayed in the grid. Users may use the pick list to select additional WMS forms.

Select the method of saving between Save and Save / Reset.

• Defaults to Save / Reset which implements current process of clearing the screen after the transaction is saved.
• Save option will bring up the same previously open transaction, in order to pick up where you left off.
• Functionality available for functions: De-Issue Inventory, Final Staging Job, Final Staging SO, Issue Job, Reserve Sales Order, and Un-Reserve Inventory.

The box is only enabled for the Issue Job, Input Production, Input Payroll Time, Final Staging Job, Final Staging Sales Orders, Reserve SO, and, beginning in version 17.02.007, the De-Issue Inventory options. The box is checked by default except for Reserve SO. This field was added to support situations where scanning GS1-128 barcodes, containing multiple AIs, was automatically committing transactions.

• Checking this box for the WMS De-issue Inventory form allows the user to decide if scanning a barcode automatically commits the quantity to be de-issued or not, and when the security setting 'WMS -- allow de-issue without physical scan' is set to No, it will allow the user to manually enter a quantity to de-issue on the WMS De-Issue Inventory form as long as a lot label is scanned first.

The box is only enabled for the Issue Job, Input Production, Final Staging Job, Final Staging Sales Orders, and De-Issue Inventory options. The box is unchecked by default. When enabled, if a barcode is scanned that is identical to the previously scanned barcode, the user will be prompted with a Yes/No prompt on whether or not this is a valid scan or not. This allows the user to ensure unwanted duplicates are not accidentally scanned. 

If checked, when using Android OS, the system will read aloud screen prompts to the user (example - "invalid PO Number"). Users can say "Repeat" to have the prompt repeated.

Modifies the selected WMS layout.

Ability to define the order in which fields will appear on the scanner for the selected WMS form layout.

Allows the user to select an already existing WMS form layout and copy all values into the new form layout.

Expiration date textbox for Physical Inventory.

• If WMS worksheet is NOT created for Physical Inventory, Expires appears (at the bottom of the form).
• If WMS worksheet is created for Physical Inventory, Expires will not appear.

When clicked, all the WMS fields in the grid will have their "Visible" flag unchecked. Users can modify individual fields as needed to change the setting.

Display only. The name of the selected control/field on the form layout.

Option to determine if the fields default value will be inserted in the selected field in the WMS scanner application.

Ability to make the control/field visible. This field is checked by default.

Applicable only for checkbox controls. Option to determine if the check box will be checked yes by default when the WMS form layout is loaded in the WMS transaction.

If checked, this field can be selected via voice recognition and the system will read the caption and data populated in this field back to the user. If the field is empty, "Empty" will be read back to the user.

• Voice recognition is configured via user settings and/or inventory options.
• When reading sales order or job numbers, the system will not read the dashes. Only the numbers will be read.
• Available for Android OS only.